AR V300R023SPH180
- There is a possibility that a device restarts unexpectedly in an Ethernet over GRE over IPsec scenario.
- After dial-up is configured on a cellular interface, there is no route to the DHCP server.
- There is a possibility that SNMP batch collection fails.
- When a device uses an IoT SIM card for network access, there is a possibility that the 5G interface flaps.
- During a restart, a device fails to start.
- The PnP button needs to be optimized.
- The console port login page does not respond.
- After a device restarts, an EVPN tunnel fails to be established using the backup link.
- A device fails to report performance data.
- When the EVPN connection of the active gateway is interrupted, the standby gateway fails to establish an EVPN connection.
- The nat assymmetric route enable command fails to be delivered to a VDSL interface in PTM mode.
- In an SD-WAN scenario, after the FEC function is enabled and the device runs for a long period time, there is a possibility that the device restarts.
- On an SD-WAN network with running IPv4 and IPv6 traffic, after the FEC function is enabled on a device and the device runs for a long period of time, there is a possibility that the device restarts.
- The gdoi sa direction receive-option command does not take effect, and the command level needs to be changed to the configuration level.
- In an SD-WAN scenario, overlay traffic statistics on WAN links reported by devices are inaccurate.
- The MTU is calculated incorrectly when IPsec is disabled for EVPN connections.
- It takes a long time to query interface management MIB objects using a tool.
- The device does not support selective QinQ on Layer 3 sub-interfaces.
- The virtual IP address of a VRRP group cannot be pinged.
- After the nat alg dns enable command is run and the device receives malformed DNS reply packets, there is a possibility that the device restarts unexpectedly.
- The IPv6 DNS service configured on a device is unavailable.
- There is a possibility that a device restarts unexpectedly if it has the function of recording NetStream logs enabled.
- Services on Ethernet sub-interfaces are interrupted.
- There is a possibility that services are interrupted for a long time on a device with IPsec services configured.
- In an SD-WAN dual-gateway scenario, there is a possibility that traffic fails to be forwarded between interconnection interfaces.
- In an SD-WAN dual-gateway scenario, there is a possibility that DNS packets fail to be forwarded.
- After per-packet load balancing is configured, a large number of packets are exchanged, affecting user experience.
- Oversized packets are incorrectly forwarded between terminals.
- In an L2TP over bridge scenario, after the traffic policy remark dscp is configured in the downstream direction, some fields in passerby packets are modified.
- The alarm generated when the number of flow table entries reaches the upper limit does not describe the reason.
- In a scenario with 160 MHz frequency bandwidth, an AR device that functions as a WLAN Fat AP restarts unexpectedly when channel calibration information is queried.
- In the scenario where DHCP assigns addresses to interfaces during RDB-based deployment, there is a possibility that the interface address configuration is lost when the device is running properly.
- The last three uptime/downtime of master and slave channels is not displayed in the channel status query result.
- In an SD-WAN scenario with active and standby links, there is a possibility that no tunnel is established over the standby link if the active link fails.
- A device with serial port redirection configured may restart after startup.
- When link flapping occurs in an SD-WAN scenario, there is a possibility that a device restarts unexpectedly.
- In an SD-WAN scenario, an alarm that indicates the current CPU usage exceeds the CPU threshold is frequently generated when a NetStream task is in progress.
- The bridge configuration of a device is lost.
- There is a possibility that a device cannot go online after going offline on the controller.
- After a user logs in to a device using SSH, the user runs the super command and then directly closes the page and logs out of the device. In this case, a semaphore leak occurs.
- A device becomes unreachable after being powered off.
- The mechanism of detecting links used by devices for controller registration is optimized to reduce resource consumption.
- The forwarding CPU usage of a device is high.
- When a large number of ping or tracert operations are interrupted unexpectedly, the memory usage keeps increasing.
- The function of disabling Telnet on a device is optimized.
- The interface information displayed on the controller is incorrect. Both ATM and Ethernet interfaces are displayed.